Don’t overwhelm your customers with features they will never care about
Image credit: Flickr
Why do I need private feature requests?
Receptive can be used to gather feature requests from customers and your internal teams. All these stakeholders will have different demands on your SaaS product and understanding them is the key to developing your product in a way which meets the strategic objectives of the company.
What you want to show you customers is entirely dependent on your SaaS business but most of us will always have features that we want to hide. Because customers and internal users have different requirements for your SaaS product there will be a level of detail or exposure that’s simply not right to share. You don’t want your customers picking through a mass of internal feature requests that aren’t relevant to them.
What sort of features should be private?
Features you might want to hide could be anything from essential maintenance requests from the development team, specific features that are for the use of internal teams only (such as customer billing reports) or even that embarrassing feature that you haven’t had time to build yet. Shhhh ;)
However…
…you probably won’t want all internal features to remain private. We always have feature requests that we discuss and define first but there often comes a time when adding customer feedback into the process becomes an incredibly valuable exercise.
With Receptive, you have complete control over which feature requests you share and when. Features can be marked as private, discussed with your internal teams then released to your customers for feedback and prioritisation when you’re ready. You can choose to keep part or all of your internal discussions private too so you control which information you share.
